Skip to content

Drop support for Ruby 3.1 - #34

Merged
vormwald merged 1 commit into
mainfrom
drop-ruby-3.1
Aug 23, 2026
Merged

Drop support for Ruby 3.1#34
vormwald merged 1 commit into
mainfrom
drop-ruby-3.1

Conversation

@vormwald

Copy link
Copy Markdown
Owner

Ruby 3.1 reached end-of-life on 2025-03-31. Keeping it in the CI matrix required pinning four transitive dev dependencies to versions predating their 3.2 floor, and that list was only going to grow — it had already caught us out twice in #30.

Changes

File Change
jekyll-tailwindcss.gemspec required_ruby_version>= 3.2.0
.github/workflows/main.yml matrix → ["3.2", "3.3", "3.4", "4.0"]
Gemfile removed the pin block: rdoc < 8, erb < 5, sass-embedded < 1.77.1, google-protobuf < 4.36
.standard.yml ruby_version 3.0 → 3.2 (stale, predated the old 3.1 floor)
CHANGELOG.md Unreleased entry
Gemfile.lock re-resolved

Lockfile effects

With the pins gone, the held-back gems move forward:

  • sass-embedded 1.77.0 → 1.103.1
  • rdoc 7.2.0 → 8.0.0
  • erb 4.0.4.1 → 6.0.7
  • google-protobuf 4.35.1 → 4.36.0
  • cgi, date, psych, stringio drop out entirely — the old erb/rdoc pulled in stdlib-extraction gems the current versions no longer need

csv, logger and base64 stay: those are unbundled in Ruby 3.4/4.0, unrelated to the 3.1 floor.

Verification

  • 33 examples, 0 failures; standardrb clean
  • All 76 locked specs, platform variants included, checked against required_ruby_version for 3.2, 3.3, 3.4 and 4.0

Note for the releaser

This is a breaking change for anyone still on 3.1. The entry sits under ## [Unreleased] — the version number is a call for release time (0.8.0 seems right).

🤖 Generated with Claude Code

https://claude.ai/code/session_015kxK16Xgi7P4GeUfkmQNxr

Ruby 3.1 went end-of-life on 2025-03-31, and keeping it in the matrix
required pinning four transitive deps (rdoc, erb, sass-embedded,
google-protobuf) to versions predating their 3.2 floor. That list was
only going to grow.

Raise required_ruby_version to >= 3.2.0, drop 3.1 from the CI matrix, and
remove the pin block so those gems resolve freely again. Also bump
.standard.yml's ruby_version from the stale 3.0 to match the new floor.

All 76 locked specs, platform variants included, resolve on ruby 3.2,
3.3, 3.4 and 4.0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015kxK16Xgi7P4GeUfkmQNxr

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The Ruby floor change is applied consistently across gemspec, CI, lint config, and dependencies, with no remaining Ruby 3.1 references affecting support.

Pull request overview

This PR drops Ruby 3.1 support across the gem’s declared requirements and CI tooling to align with Ruby 3.1’s EOL and remove the need for transitive dev-dependency pinning.

Changes:

  • Bump the gem’s minimum supported Ruby to >= 3.2.0 and align StandardRB’s configured Ruby version to 3.2.
  • Update CI to stop testing Ruby 3.1 and test 3.2, 3.3, 3.4, and 4.0 instead.
  • Remove Ruby-3.1-era dependency pins and re-resolve the lockfile; document the breaking change in the changelog.
File summaries
File Description
jekyll-tailwindcss.gemspec Raises required_ruby_version to >= 3.2.0.
.github/workflows/main.yml Removes Ruby 3.1 from the CI matrix.
Gemfile Deletes now-unnecessary pins for transitive dev dependencies.
Gemfile.lock Updates resolved versions consistent with the removed pins and new Ruby floor.
.standard.yml Aligns StandardRB’s ruby_version setting with the new minimum Ruby.
CHANGELOG.md Adds an Unreleased entry noting Ruby 3.1 support removal.
Review details
  • Files reviewed: 5/6 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@vormwald
vormwald merged commit 866d468 into main Aug 23, 2026
5 checks passed
@vormwald
vormwald deleted the drop-ruby-3.1 branch August 23, 2026 03:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants